Systems and methods for personalized care management

ABSTRACT

Disclosed are systems and methods for personalized care management. A plurality of user devices corresponding to a plurality of authorized caregivers are configured to provide input data to a processing module 1004. The input data is associated with an actionable item being performed for at least one care receiver, wherein the actionable item includes one of: a scheduled actionable item and a non-scheduled actionable item. The processing module 1004 receives, the at least one input data based on the scheduled actionable item and the non-scheduled actionable item. A profile of the at least one care receiver is updated based on the received at least one input data, and thereafter stored in a database 1010. The plurality of authorized caregivers is facilitated to access the stored updated profiles of the at least one care receiver for further analysis.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material,which is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever. 37 CFR 1.71(d).

TECHNICAL FIELD

The disclosed subject matter relates to a system and method forpersonalized resident care management, more particularly the disclosedsubject matter relates to a system and method to personalize informationpresentation to a user on a user device based on a specific assignedrole to the user. Resident care management refers to managing the carefor residents in an institutional setting such as an assisted livingfacility for the elderly. Care refers to both clinical (i.e. medical,behavioral) and non-clinical, i.e. social activities.

BACKGROUND

Resident care management solutions help care givers such as medicalattendants, doctors, nurses, nursing assistants, spouses, familymembers, etc. These solutions help to maintain a smooth flow ofinformation from one stop to the other. This helps in no break ininformation exchange. Also, since there are no breaks in informationexchange hence, they make caregivers efficient.

However, the existing solutions are labor intensive. In most cases thereis no electronic system and caregivers use manual processes. In caseswhere there are electronic systems, User has to complete a lot offormalities and has to process and fill information from various screensand interfaces. Such process makes task difficult and the objective ofthe smooth flow of information is not met. Further, there is also noautomation within such solutions that helps other users to be informedwhen there is any modification or actionable item generated for them byone or more user(s).

Another drawback of such solution is that there is no customization ofinterface for different users. Also, there is no escalation procedure incase the actionable item is not fulfilled.

Therefore, there exists a need for an efficient care/resident managementsolution.

SUMMARY

This summary is provided to introduce concepts related to system andmethod for personalized resident care management concepts are furtherdescribed in the detailed description. This summary is not intended toidentify essential features of the claimed subject matter nor is itintended for use in determining or limiting the scope of the claimedsubject matter.

In an implementation, a system for personalized care management isdisclosed. The system may comprise a plurality of user devicescorresponding to a plurality of users. Each user of the plurality ofusers have a specific assigned role. Further, each user device of theplurality of user devices provide an interactive user interface to itscorresponding user. The system further includes a central controllerthat is connected to the plurality of user devices through a network.The central controller may comprise a processing module that may performthe steps comprising of receiving login credentials of the user throughthe user interface provided on the user device. The provided credentialsare then cross checked, from a database. The database may store user IDsand corresponding credentials of the plurality of users. After this theprocessing module, retrieves a specific role assigned to the user andmodifies information read/write layout based on the specific assignedrole of the user.

In another implementation, a method for personalized care management isdisclosed. The method may include the step of storing, in a database,profiles of a plurality of users. The method further includesregistering, in the database, at least one corresponding user device foreach of the plurality of users. Furthermore, the method may include stepof receiving login credentials of the user through an interactive userinterface that is provided on the user device. The method may furtherinclude, matching, by the processor, the login credentials received forauthentication. The processor then, retrieves profile of the user postauthentication and based on the profile of the user, information layoutof the user interface presented to the user is modified.

Yet another embodiment of the present disclosure provides acommunication system for providing personalized care managementcomprising: a plurality of user devices corresponding to a plurality ofauthorized caregivers, each user device providing an interactive userinterface to: provide input data associated with an actionable itembeing performed for at least one care receiver, wherein the actionableitem includes one of: a scheduled actionable item and a non-scheduledactionable item; a database for storing profiles of the authorizedcaregivers and profiles of the at least one care receiver; a centralcontroller connected to the plurality of user devices through acommunication network to facilitate the authorized caregivers to analyzethe profiles of the at least one care receiver from a remote location;the central controller comprising a processing module configured to:receive, via the plurality of user devices, the at least one input databased on the scheduled actionable item; receive, via the plurality ofuser devices, the at least one input data based on the non-scheduledactionable item; update the profile of the at least one care receiverbased on the received at least one input data; save the updated profileof the at least one care receiver in the database; and facilitate theauthorized caregivers to further analyze the updated profile of the atleast one care receiver.

In an aspect of the present disclosure, the profiles of the authorizedcaregivers are stored in different formats based on specific rolesassigned to the authorized caregivers, and location of the plurality ofuser devices.

In an aspect of the present disclosure, the authorized caregiversinclude at least one of: a family member of the care receiver, anattendant for the care receiver, a nurse for the care receiver, a doctorfor the care receiver, or a medicine administrator for the carereceiver.

In an aspect of the present disclosure, the network is a wired or awireless network, wherein the wireless network comprising at least oneof: a mobile network, a satellite network, a Wi-Fi, or a Wireless LocalArea Network (WLAN).

In an aspect of the present disclosure, the at least one input dataincludes a voice input, a text input, a video input, and a touch-basedinput.

In an aspect of the present disclosure, the actionable item includesmedical care, psychological care, non-medical care, daily routine care,being provided to the at least one care-receiver by the plurality ofauthorized caregivers.

In an aspect of the present disclosure, the at least one input databased on the non-scheduled actionable item is inputted into theprocessing module through at least one QR Code scanner device.

In an aspect of the present disclosure, the at least one input databased on the non-scheduled actionable item is inputted into theprocessing module through at least one Beacon Transmitter.

In an aspect of the present disclosure, the non-scheduled actionableitem includes one or more actions which are performed randomly for thecare receiver.

In an aspect of the present disclosure, the scheduled actionable itemincludes one or more actions which are performed for the care receiver,according to a schedule prescribed by the corresponding authorizedcaregivers.

Yet another embodiment of the present disclosure provides a method forproviding personalized care/resident management. The method comprisesthe steps of: configuring a plurality of user devices corresponding to aplurality of authorized caregivers, each user device providing aninteractive user interface for: providing input data associated with anactionable item being performed for at least one care receiver, whereinthe actionable item includes one of: a scheduled actionable item and anon-scheduled actionable item; configuring a database for storingprofiles of the authorized caregivers and profiles of the at least onecare receiver; configuring a central controller connected to theplurality of user devices through a communication network forfacilitating the authorized caregivers to analyze the profiles of the atleast one care receiver from a remote location; configuring a processingmodule for: receiving, via the plurality of user devices, the at leastone input data based on the scheduled actionable item; receiving, viathe plurality of user devices, the at least one input data based on thenon-scheduled actionable item; updating the profile of the at least onecare receiver based on the received at least one input data; saving theupdated profile of the at least one care receiver in the database; andfacilitating the authorized caregivers to further analyze the updatedprofile of the at least one care receiver.

Other and further aspects and features of the disclosure will be evidentfrom reading the following detailed description of the embodiments,which are intended to illustrate, not limit, the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The illustrated embodiments of the subject matter will be bestunderstood by reference to the drawings, wherein like parts aredesignated by like numerals throughout. The following description isintended only by way of example, and simply illustrates certain selectedembodiments of devices, systems, and processes that are consistent withthe subject matter as claimed herein.

FIG. 1 illustrates a system, in accordance with aspects of theembodiments;

FIG. 2 is a diagram illustrating components within a processor, inaccordance with aspects of the embodiments;

FIG. 3 is a table illustrating information layout accessibility, inaccordance with aspects of the embodiments;

FIG. 4 is a flow chart diagram illustrating overall method ofcare/resident management tracking, in accordance with an aspect of theembodiments;

FIG. 5 is a flow chart diagram illustrating method generating secondnotifications for care/resident management tracking, in accordance withan aspect of the embodiments;

FIG. 6 is a flow chart diagram illustrating modifying notificationsformats, in accordance with an aspect of the embodiments;

FIG. 7 is a block diagram of an exemplary computer system, in accordancewith an aspect of the embodiments;

FIG. 8 is a diagram illustrating various user interfaces for users withdifferent roles, in accordance with an aspect of the embodiments;

FIGS. 9A-9D are diagrams illustrating various information dashboards forvarious user with different roles, in accordance with an aspect of theembodiments;

FIG. 10 is a block diagram illustrating system elements of a centralcontroller of a communication system, in accordance with an embodimentof the present disclosure; and

FIG. 11 is a block diagram illustrating system elements of the centralcontroller communicating with external devices to receive input datarelated to non-scheduled actionable items, in accordance with anembodiment of the present disclosure.

DETAILED DESCRIPTION

A few inventive aspects of the disclosed embodiments are explained indetail below with reference to the various figures. Embodiments aredescribed to illustrate the disclosed subject matter, not to limit itsscope, which is defined by the claims. Those of ordinary skill in theart will recognize a number of equivalent variations of the variousfeatures provided in the description that follows.

Reference throughout the specification to “various embodiments,” “someembodiments,” “one embodiment,” or “an embodiment” means that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Thus,appearances of the phrases “in various embodiments,” “in someembodiments,” “in one embodiment,” or “in an embodiment” in placesthroughout the specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures orcharacteristics may be combined in any suitable manner in one or moreembodiments.

FIG. 1 illustrates a system 100, in accordance with aspects of theembodiments. a block diagram of a system 100 for personalizedcare/resident management, is illustrated in accordance with anembodiment. The system 100 may include one or more of a processor,memory that includes a temporary transient (volatile) memory such asRandom-Access Memory (RAM) and a computer readable medium or article(not shown in FIG. 1).

The system 100 includes a plurality of user devices 102 a-102 n(collectively referred to as 102) corresponding to a plurality of users103 a-103 n (collectively referred to as 103). Each of the users 103have at least one corresponding user device 104 registered. In otherimplementations, the user 103 may have multiple user devices registered.Also, each of the user may have a specific role assigned to the user 103or a profile. The system further includes a central controller 105. Thecentral controller 105 is connected to the plurality of user devices 102through a network 104.

The central controller 105 may further include a transceiver 106, aprocessor 108, a notification distribution module 112 and a database110.

In an implementation, the specific role assigned to the user may be adoctor, a nurse, an attendant, a medicine administrator, or a familymember/relative.

In another implementation, the network 104 may be a wireless network, awired network, or a combination thereof. The network 104 can beimplemented as one of the different types of networks, such as intranet,local area network (LAN), wide area network (WAN), the internet, and thelike. The network 104 may either be a dedicated network or a sharednetwork. The shared network represents an association of the differenttypes of networks that use a variety of protocols, for example,Hypertext Transfer Protocol (HTTP), Transmission ControlProtocol/Internet Protocol (TCP/IP), Wireless Application Protocol(WAP), and the like, to communicate with one another. Further thenetwork 104 may include a variety of network devices, including routers,bridges, servers, computing devices, storage devices, and the like.

The central controller 105 may include at least one processor, aninput/output (I/O) interface and a database 110. The at least oneprocessor may be implemented as one or more microprocessors,microcomputers, microcontrollers, digital signal processors, centralprocessing units, state machines, logic circuitries, and/or any devicesthat manipulate signals based on operational instructions. Among othercapabilities, the at least one processor is configured to fetch andexecute computer-readable instructions stored in the database 110.

The database 110 may either be a primary memory or a secondary memory.For example, but not restricted to, random access memory (RAM), cachememory, hard disk drive (HDD), solid state drive (SSD), compact disk(CD), portable memories, and like.

By way of an example, the system 100 may be a system to accessresident's details by the plurality of users 103. Each of the users outof the plurality of the users 103 may login to a same informationbackplane. The information backplane may be of an assisted living home,a hospital, or any other similar patient managing place. However, it maybe apparent to a person having ordinary skill in the art to apply thesystem as described in any other implementation with similarcharacteristics.

Still referring to FIG. 1 each of the plurality of users 103 (user andplurality of user will be interchangeably referred as 103) has at leastone user device. Each user device 103 may have a software applicationthat needs to be installed on the user device 103. The softwareapplication may be an Android application or an iOS application, awindows application, or any other user device application or a webapplication. A user interface is presented to the user once the user 103accesses it. The user interface may be accessed using touch or webinterface. User 103, may have to enter login credentials that mayinclude a user ID and a password. The database 110 may store multipleuser ID and passwords that may have been collected at the time ofregistration of the user 103. The user 103 may have at least one userdevice registered. The database 110 may also include profile of the user103 that may further include a specific assigned role to the user 103.The specific assigned role helps in determining access that the user 103might have to information on user interface. The profile of the user 103may also help in identifying to what all information does the user 103has access.

Once the user 103, wanting to access details of one or multipleresidents, may input login credentials on the user interface, thisinformation is sent to the central controller 105. As disclosed earlier,the user device 104 and the central controller may be connected throughthe network 104. The central controller 105 receives the logincredentials of the user 103 through a transceiver 106. The transceiver106 may be connected to the processor 108. The received logincredentials may be forwarded by the transceiver 106 to the processor108. The processor 108, may query the database to check and authenticatethe user. In case the login credentials do not match, the processor 108may send a notification message describing authentication failure,through the transceiver 106, that may be displayed on the userinterface. However, in case the login credentials provided match withthe details on the database 110, the processor 108 may then fetch theprofile of the user 103. The profile of the user 103 may include detailsabout specific role assigned, the devices the user is allowed access to(e.g. shared mobile device, web computer, personal mobile device, etc.),the times the user is allowed access to the system (e.g. in a shiftbased environment user may not be allowed to access the system if theyare not the shift schedule). In another implementation user device 104may be a shared device wherein a person may use the device 104 for sometime and then handover to other person. Based on the specific roleassigned or based on the profile of the user 103, the processor 108, maythen provide an information read/write layout. The data presentationwithin the information read/write layout may be modified with changingusers and their assigned specific roles or profiles. For e.g. theinformation read/write layout for a doctor may have more information toread or write than a nurse who may have access to only profile data of aresident or medication data. Hence, as per the profile of the user 103,landing page and other related information displayed on the informationread/write layout and its display may change.

Still referring to FIG. 1, the processor 108 (or the processing module108) is also connected to the notification distribution module 112. Ifthe user 103, after logging in to the information read/write layoutperforms certain operation or interacts with the data, there may be anotification that may be generated by the processor 108. Thenotification may either be a knowledge item that is, it only containsread information. Further, the notification may have an actionable itemthat the user 103 may have suggested or instructed for a second user.This notification is then communicated by the notification distributionmodule 112 to corresponding user device of another user. Thenotification distribution module 112 may format the notification basedon a plurality of factors. The format of the notifications may be basedon type of notifications being opted, destination user of thenotification, time of the notification, location of the destinationuser, or type user device registered for receiving notifications. Basedon the information of all these factors, the notification distributionmodule 112 may format the notifications in a such a manner so as to keepdata private. Therefore, if user to whom the notification is to bedelivered, is in a public place as per his location details thencomplete information is not sent. Only an indicative information isforwarded. So, for e.g. if the user 103 wants to send a notification toa family member/relative of a resident, he may send it through theinformation read/write layout. However, the notification may have suchinformation that may not be displayed completely in a public place assome other person might see it and hence compromise data security.Therefore, the information is sent in an indicative manner to inform therelative that something has happened to the resident without disclosingname etc. This message can be comprehended by the relative itself.

Referring now to FIG. 2, a diagram illustrating internal components ormodules within the processor 108. The processor 108 may include a datacollection engine 1082, a user authentication engine 1086, a layoutdetermination engine 1088 and a notification generation engine 1084.

The data collection engine 1082, may receive data from the transceiver106 of the central controller 105. The data collected may include userlogin credentials, location data, device used, time of login, etc. thedata collection engine 1082 may make a local repository (not shown inthe figure). The local repository may store the data collected forfurther use. A part of data collected may be forwarded to the userauthentication engine 1086 and other part may be forwarded to thenotification determination engine 1084 simultaneously. The userauthentication engine 1086 may receive the part with the usercredentials and communicates with the database 110 of the centralcontroller 105. The user credentials received may be cross checked bythe user authentication engine 1086 with the database 110. In case theuser credentials are wrong, a display notification of userauthentication failure may be sent via the transceiver 106 to userinterface of the user device 102. Authentication of a user may also bebased on approved or registered devices, device determined to be used,or on specific timing a user is supposed to login. In case, the usercredentials or other data as described above are authenticated, profileof the user 103 is also retrieved by the user authentication engine. Theprofile may be then forwarded simultaneously to the layout determinationengine 1088 and the notification generation engine 1084. The layoutdetermination engine 1088, as per the received profile and specific roleinformation within the profile, may modify information and presents theinformation read/write layout to the user 103 on the user interface ofthe user device 104. Further, the notification generation engine 1084may continuously monitor user's activity on the information read/writelayout. When the user 103 interacts with the information read/writelayout in a manner that may need a follow up interaction of anotheruser, a notification may be automatically generated. In anotherimplementation, the notification may be generated by action of the user103.

By way of an example in the case of a fall of an individual, anotification is sent to the care givers, another notification sent toadministrator, a 3^(rd) notification is sent to the family. By way ofanother example, in case a doctor logged in wants a follow up on effecta prescribed medicine prescribed may generate two notificationsautomatically. One notification may be generated and may require a nurseto keep noting medicine effect on the resident that the nurse may haveto update periodically. While the second notification may be for themedicine administrator who will have to administer the prescribedmedicine. In other implementation, a third notification may also begenerated for the relative of the resident indicating new medicineprescribed. Hence, the first two notifications may be due to anactionable item needed to be performed by other users and the thirdnotification may be due to an information item needed to be provided toanother user. Also, the plurality of users 103 may be arranged in ahierarchical order. The hierarchical order may describe the informationread/write layout access. The person at the top of the hierarchy mayhave access to all the information. The person at the bottom of theorder may have only read access of the data.

The notification generation engine 1084 may also monitor the generatednotifications and the actionable item attached to the notification. Incase, there is an actionable item generated for a second user that isnot completed within a certain time limit, the notification generationengine 1084 may generate a second notification to a third user who isabove in hierarchy from the second user. Time limit may be user definedor system defined. System may be able to read information and set up atime limit for the actionable item itself.

Now referring to FIG. 3, illustrates a table depicting informationlayout accessibility. The accessibility may be based upon the user rolein the system 100. For e.g. the doctor may have access to fullinformation and full rights of read/write operations. Whereas, anattendant may only have a partial access that may include only readaccess. The table may also define the hierarchy order within the system100 to define read/write rights.

Now referring to FIG. 4, illustrating a flowchart method 400 forpersonalized care/resident tracking. At step 402, the central controller105 stores profiles of the plurality of users 102. The profile mayinclude data like hierarchical rank, location data, specific role, userdevice, etc. The profile may be stored within the database 110. In animplementation, this profile may be either collected while registrationof the user 103. In other implementation, the profile may beautomatically collected. For e.g. location data, user device type, etc.

At step 404, a corresponding user device for the user 103 is alsoregistered along with user registration. At step 406, the centralcontroller 105 receives login credentials of the user 103. Thecredentials are received through the user interface presented on theuser device 102. The user interface, presented on the user device 102,may be through a software application installed on the user device, orthrough a web interface. Further, at step 408, authentication of thereceived user credentials is done. The received user credentials arematched with the user's data stored within the database 110. In case theauthentication fails, the user 103 receives an “authentication failed”notification displayed on display of the user interface. However, on asuccessful match, the processor 108, at step 410, retrieves the profileof the user 103. The retrieved profile may include the accessibilitydata or specific assigned role for the user 103. Based on the specificrole assigned to the user 103, the information read/write layout ismodified at step 412. That is the information to be presented to aspecific type of user depends upon the specific role of a user. Hence, adoctor may have a different layout presented when compared to a nurse ora relative.

Now referring to FIG. 5, a flow chart illustrating a method 500 togenerate second notifications is disclosed. At step 502, the processor108, receives login credentials of the user 103. The credentials arecollected through the interface of the software application initiated bythe user 103. The credentials are sent through the network 104 andreceived by the transceiver 106 that forwards the details to theprocessor 108. The processor 108, then at step 508, matched the receivedcredentials with the credentials stored in the database 110. On asuccessful authentication the processor 108, at step 506, retrieves theprofile of the user 103. The retrieved profile may include theaccessibility data or specific assigned role for the user 103. Further,at step 508, the processor 108 modifies the information read/wrotelayout as per the profile of the user 103. If the user 103, interactswith the information read/write layout in any manner, then at step 510,the processor 108 generates the notification. The notification may be anactionable item or an information item intended for the second user. Atstep 512, the notification distribution module 112, connected to theprocessor 108, may determine format of the notification generated. Asalso disclosed above, the format of the notifications may be based ontype of notifications being opted, destination user of the notification,time of the notification, location of the destination user, or type userdevice registered for receiving notifications. Based on the informationof all these factors, the notification distribution module 112 mayformat the notifications in such a manner so as to keep data private.

At step 514 a, the processor determines, whether the generatednotification has an actionable item or not. In case, the notificationonly has a knowledge item, then at step 514 b, the notification is sentintended user to be displayed on his user device. The format of thenotification is based on the format as decided by the notificationdistribution module 112 as described above. However, in case thenotification includes an actionable item, then at step 516, theprocessor determines time limit, if mentioned or desired, within whichthe actionable item needs to be performed. Further, at step 518, theprocessor may keep a check that whether the actionable item has beentaken care of or not by the second user. In case the actionable item hasbeen attended to by the second user, the method may be ended and a newprocess may be started. However, in case the second user has not takencare of the actionable item within the time limit prescribed by thefirst user or by processor, then the notification generation engine 1084may generate a second notification for third user at step 520. Asdescribed above the plurality of users 103 may be arranged in ahierarchy. Hence, the third user is higher in hierarchy than the seconduser.

Now referring to FIG. 6, illustrating a flow chart depicting a method600 to modify notification formats, in accordance with an aspect of theembodiments. As disclosed above format of the notifications may be basedon type of notifications being opted, destination user of thenotification, time of the notification, location of the destinationuser, or type user device registered for receiving notifications. In animplementation, notifications may be like medication being refused by aresident, a fall by a resident, supplies provided by the family beingrun out, resident out of medication, visitor coming to see a resident, aphysician doing a check up on a resident, etc. In anotherimplementation, the notifications may also be based on the timing of useof the shared device 104. In another implementation users may “checkout” a device 104 and use it during the course of a shift. The device104 in use may be different at different times or days. It may becorrectly determined on what device 104, the notification should be sentto, based on what shared device is being used.

Based on the information of all these factors, the notificationdistribution module 112 may format the notifications in a such a mannerso as to keep data private. Therefore, if user to whom the notificationis to be delivered, is in a public place as per his location detailsthen complete information is not sent. Only an indicative information isforwarded. So, for e.g. if the user 103 wants to send a notification toa family member/relative of a resident, he may send it through theinformation read/write layout. However, the notification may have suchinformation that may not be displayed completely in a public place assome other person might see it and hence compromise data security.Therefore, the information is sent in an indicative manner to inform therelative that something has happened to the resident without disclosingname etc. This message can be comprehended by the relative itself.

Referring back to FIG. 6, at step 602 the notification generation engine1084 may receive a notification generation request. The notification maybe generated when user 103 interacts with the information read/writelayout. In an implementation, the notification may be generated bysystem 100 itself. For e.g. when medication time for the patient haselapsed above a threshold time, a notification may be generated for themedication assistant.

Further at step 604 a check is done determining whether the user 103 haschosen any specific format or not. If the user 103 has a specific formatset for the notification, the notification may be then sent to the user103 in that specified format at step 614.

However, in case there is no specific format chosen by the user 103,then at step 606 a, the notification distribution module 112 maydetermine whether there is any specific time chosen by the user 103. Incase there is a specific time chosen by the user 103, then at step 606 bformat of the notification is modified as per the time of the day. Fore.g. in case the time for notifications chosen by the user is a timethat generally falls after office hours or at a time that generallyfalls when the user 103 may be alone, then the notification is modifiedas per the time. In an implementation, notifications may be sent out atall times, e.g. urgent notifications. Urgent notification may be on theoccasion of a fall, or a resident being sent to a hospital. In case, theuser 103 has not chosen any specific time, then at step 608, thenotification distribution module determines the registered device forthe user 103. The registered user device may be categorized further as ahome device, shared device or out of home device or any other categoryof device. At step 610, the location of the user device is determined.Location details may be collected from location capturing components ofthe user device. Various devices include GPS chips to identify andcollect location details. These details may be collected bycommunicating with the user device 102 or while the user 103 logs in tothe system 100. The processor 108 may identify the location as residenceor public place in relation to time. At step 612, the notificationmodule 112 determines the format of the notification. Therefore, if userto whom the notification is to be delivered, is in a public place as perhis location details then complete information is not sent. Only anindicative information is forwarded. So, for e.g. if the user 103 wantsto send a notification to a family member/relative of a resident, he maysend it through the information read/write layout. However, thenotification may have such information that may not be displayedcompletely in a public place as some other person might see it and hencecompromise data security. Therefore, the information is sent in anindicative manner to inform the relative that something has happened tothe resident without disclosing name etc. This message can becomprehended by the relative itself. At step 614, the notification istransmitted in the determined format.

Now referring to FIG. 7, illustrating a block diagram of an exemplarycomputer system 702 for implementing various embodiments is disclosed.Computer system 702 may comprise a central processing unit (“CPU” or“processor”) 704. Processor 704 may comprise at least one data processorfor executing program components for executing user- or system-generatedrequests. A user may include a person, a person using a device such assuch as those included in this disclosure, or such a device itself.Processor 704 may include specialized processing units such asintegrated system (bus) controllers, memory management control units,floating point units, graphics processing units, digital signalprocessing units, etc. Processor 704 may include a microprocessor, suchas AMD Athlon, Duron or Opteron, ARM's application, embedded or secureprocessors, IBM PowerPC, Intel's Core, Itanium, Xeon, Celeron or otherline of processors, etc. Processor 704 may be implemented usingmainframe, distributed processor, multi-core, parallel, grid, or otherarchitectures. Some embodiments may utilize embedded technologies likeapplication-specific integrated circuits (ASICs), digital signalprocessors (DSPs), Field Programmable Gate Arrays (FPGAs), etc.

Processor 704 may be disposed in communication with one or moreinput/output (I/O) devices via an I/O interface 706. I/O interface 706may employ communication protocols/methods such as, without limitation,audio, analog, digital, monoaural, RCA, stereo, IEEE-1394, serial bus,universal serial bus (USB), infrared, PS/2, BNC, coaxial, component,composite, digital visual interface (DVI), high-definition multimediainterface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n/b/g/n/x,Bluetooth, cellular (e.g., code-division multiple access (CDMA),high-speed packet access (HSPA+), global system for mobilecommunications (GSM), long-term evolution (LTE), WiMax, or the like),etc.

Using I/O interface 706, computer system 702 may communicate with one ormore I/O devices. For example, an input device 708 may be an antenna,keyboard, mouse, joystick, (infrared) remote control, camera, cardreader, fax machine, dongle, biometric reader, microphone, touch screen,touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS,gyroscope, proximity sensor, or the like), stylus, scanner, storagedevice, transceiver, video device/source, visors, etc. An output device710 may be a printer, fax machine, video display (e.g., cathode ray tube(CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma,or the like), audio speaker, etc. In some embodiments, a transceiver 712may be disposed in connection with processor 704. Transceiver 712 mayfacilitate various types of wireless transmission or reception. Forexample, transceiver 712 may include an antenna operatively connected toa transceiver chip (e.g., Texas Instruments WiLink WL1283, BroadcomBCM4760IUB8, Infineon Technologies X-Gold 618-PMB9800, or the like),providing IEEE 802.11a/b/g/n, Bluetooth, FM, global positioning system(GPS), 2G/3G HSDPA/HSUPA communications, etc.

In some embodiments, processor 704 may be disposed in communication witha communication network 714 via a network interface 716. Networkinterface 716 may communicate with communication network 714. Networkinterface 716 may employ connection protocols including, withoutlimitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000Base T), transmission control protocol/internet protocol (TCP/IP), tokenring, IEEE 802.11a/b/g/n/x, etc. Communication network 714 may include,without limitation, a direct interconnection, local area network (LAN),wide area network (WAN), wireless network (e.g., using WirelessApplication Protocol), the Internet, etc. Using network interface 716and communication network 714, computer system 702 may communicate withdevices 718, 720, and 722. These devices may include, withoutlimitation, personal computer(s), server(s), fax machines, printers,scanners, various mobile devices such as cellular telephones,smartphones (e.g., Apple iPhone, Blackberry, Android-based phones,etc.), tablet computers, wearable device such as a smart watch, eBookreaders (Amazon Kindle, Nook, etc.), laptop computers, notebooks, gamingconsoles (Microsoft Xbox, Nintendo DS, Sony PlayStation, etc.), or thelike. In some embodiments, the computer system 602 may itself embody oneor more of these devices.

In some embodiments, processor 704 may be disposed in communication withone or more memory devices (e.g., a RAM 726, a ROM 728, etc.) via astorage interface 724. Storage interface 724 may connect to memorydevices 730 including, without limitation, memory drives, removable discdrives, etc., employing connection protocols such as serial advancedtechnology attachment (SATA), integrated drive electronics (IDE),IEEE-1394, universal serial bus (USB), fiber channel, small computersystems interface (SCSI), etc. The memory drives may further include adrum, magnetic disc drive, magneto-optical drive, optical drive,redundant array of independent discs (RAID), solid-state memory devices,solid-state drives, etc.

Memory devices 730 may store a collection of program or databasecomponents, including, without limitation, an operating system 732, auser interface application 734, a web browser 736, a mail server 738, amail client 740, a user/application data 742 (e.g., any data variablesor data records discussed in this disclosure), etc. Operating system 732may facilitate resource management and operation of computer system 702.Examples of operating system 732 include, without limitation, AppleMacintosh OS X, Unix, Unix-like system distributions (e.g., BerkeleySoftware Distribution (BSD), FreeBSD, NetBSD, OpenBSD, etc.), Linuxdistributions (e.g., Red Hat, Ubuntu, Kubuntu, etc.), IBM OS/2,Microsoft Windows (XP, Vista/7/8, etc.), Apple iOS, Google Android,Blackberry OS, or the like. User interface 734 may facilitate display,execution, interaction, manipulation, or operation of program componentsthrough textual or graphical facilities. For example, user interfacesmay provide computer interaction interface elements on a display systemoperatively connected to computer system 702, such as cursors, icons,check boxes, menus, scrollers, windows, widgets, etc. Graphical userinterfaces (GUIs) may be employed, including, without limitation, AppleMacintosh operating systems' Aqua, IBM OS/2, Microsoft Windows (e.g.,Aero, Metro, etc.), Unix X-Windows, web interface libraries (e.g.,ActiveX, Java, Javascript, AJAX, HTML, Adobe Flash, etc.), or the like.

In some embodiments, computer system 702 may implement web browser 736stored program component. Web browser 736 may be a hypertext viewingapplication, such as Microsoft Internet Explorer, Google Chrome, MozillaFirefox, Apple Safari, etc. Secure web browsing may be provided usingHTTPS (secure hypertext transport protocol), secure sockets layer (SSL),Transport Layer Security (TLS), etc. Web browsers may utilize facilitiessuch as AJAX, DHTML, Adobe Flash, JavaScript, Java, applicationprogramming interfaces (APIs), etc. In some embodiments, computer system702 may implement mail server 738 stored program component. Mail server738 may be an Internet mail server such as Microsoft Exchange, or thelike. Mail server 738 may utilize facilities such as ASP, ActiveX, ANSIC++/C#, Microsoft .NET, CGI scripts, Java, JavaScript, PERL, PHP,Python, WebObjects, etc. Mail server 738 may utilize communicationprotocols such as internet message access protocol (IMAP), messagingapplication programming interface (MAPI), Microsoft Exchange, postoffice protocol (POP), simple mail transfer protocol (SMTP), or thelike. In some embodiments, computer system 702 may implement mail client740 stored program component. Mail client 740 may be a mail viewingapplication, such as Apple Mail, Microsoft Entourage, Microsoft Outlook,Mozilla Thunderbird, etc.

In some embodiments, computer system 702 may store user/application data742, such as the data, variables, records, etc. as described in thisdisclosure. Such databases may be implemented as fault-tolerant,relational, non-relational, scalable, secure databases such as MicrosoftSQL server, Oracle, NoSQL, grpahy or Sybase. Alternatively, suchdatabases may be implemented using standardized data structures, such asan array, hash, linked list, struct, structured text file (e.g., XML),table, or as object-oriented databases (e.g., using ObjectStore, Poet,Zope, etc.). Such databases may be consolidated or distributed,sometimes among the various computer systems discussed above in thisdisclosure. It is to be understood that the structure and operation ofthe any computer or database component may be combined, consolidated, ordistributed in any working combination.

Now referring to FIG. 8, illustrating various user interfaces for userswith different roles, in accordance with an aspect of the embodiments.As discussed above, the information read/write layout is modified as perthe specific role or profile of the plurality of users 103. The userinterface 800 is an exemplary login page for a mobile phone. Similaruser interfaces may be provided on any type of user device. The userinterface 800 may be generated when the user 103 activates a softwareapplication on the user devices or opens up a web page for the same. Theuser interface 800 includes a username field 802 and a password field804. In other implementation, user login may also be biometric basedlike fingerprints, pulse or other biosensor related data that may beprocessed as a bio-print. After logging in with registered credentials,the user 103 may be authenticated. On authentication, the profile of theuser 103 is accessed. Based on the user profile, specific role of theuser is determined and the layout determination engine 1088 determinesthe information read/write layout of the user interface 800. If the user103 is a doctor, the information read/write layout is as shown by userinterface 806. This layout may display all residents or patientsavailable and mapped to the doctor. User interface 808, displaysinformation read/write layout if the user 103 is logged in is a nurse.Noticeable is the difference between the user interface 806 and userinterface 808. Number of residents may be different. Further, userinterface 810 displays user interface if the user 103 logged in is amedicine administrator. Similarly, if the user 103 is a familymember/relative, the user interface 812 is presented.

FIGS. 9a -9d illustrates various user interface dashboard 900 based onspecific roles assigned to users. As disclosed in FIG. 9a , thedashboard 900 has items field 902 based on the user 103 being a doctor.As may be observed, the items presented in items field 902 are many innumber and hence may be only presented to a doctor. Further, as shown inFIG. 9b , the items field 904 displays a little less information as theuser 103 logged in is a nurse. Similarly, the items field 906 depictedin FIG. 9c and items field 908 depicted in FIG. 9d may be presented forthe user 103 being a medicine administrator and a family member/relativerespectively. The change in the items in the items fields 902, 904, 906,and 908 may be observed. The change in the items is due to the specificrole of the user 103 logged in to the system 100.

FIG. 10 is a block diagram 1000 illustrating system elements of acentral controller 1002 of a communication system, in accordance with anembodiment of the present disclosure. As shown, the central controller1002 includes a processing module 1004, a notification distributionmodule 1006, a voice processor 1008, and a database 1010.

The communication system includes a plurality of user devicescorresponding to a plurality of users. Each user of the plurality ofusers has a specific assigned role. Further, each user device of theplurality of user devices presents an interactive user interface to thecorresponding user. Non-limiting examples of the plurality of userdevices may include a television, a smartphone, a tablet computer, asmart watch, a fitness tracker, a laptop computer, a desktop computer, apersonal digital assistant, a smart television, or a wearable device.Further, the network may be a wired or a wireless network. Examples ofthe wireless network may include, but are not limited to, a mobilenetwork, a satellite network, a Wi-Fi, or a Wireless local area network(WLAN).

The central controller 1004 is connected to the plurality of userdevices through a network. The central controller 1004 includes theprocessing module 1004 configured to receive login credentials of theuser through the user interface. The processing module 1004 may beimplemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. Among other capabilities, theprocessing module 1004 is configured to fetch and executecomputer-readable instructions stored in the database 1010.

The database 1010 may either be a primary memory or a secondary memory.For example, but not restricted to, random access memory (RAM), cachememory, hard disk drive (HDD), solid state drive (SSD), compact disk(CD), portable memories, and like.

By way of an example, the communication system may be a system to accessresident's details by the plurality of users. Each of the users out ofthe plurality of the users may login to a same information backplane.The information backplane may be of an assisted living home, a hospital,or any other similar patient managing place. However, it may be apparentto a person having ordinary skill in the art to apply the system asdescribed in any other implementation with similar characteristics.

Each of the plurality of users has at least one user device. Each userdevice may have a software application that needs to be installed on theuser device. The software application may be an Android application oran iOS application, a windows application, or any other user deviceapplication or a web application. A user interface is presented to theuser once the user accesses it. The user interface may be accessed usingtouch or web interface. User may have to enter login credentials thatmay include a user ID and a password. The database 1010 may storemultiple user ID and passwords that may have been collected at the timeof registration of the user. The user may have at least one user deviceregistered. The database 1010 may also include profile of the user thatmay further include a specific assigned role to the user. The specificassigned role helps in determining access that the user might have toinformation on user interface. The profile of the user may also help inidentifying to what all information does the user have access.

Once the user, wanting to access details of one or multiple residents,may input login credentials on the user interface, this information issent to the central controller 1002. As disclosed earlier, the userdevice and the central controller 1002 may be connected through thenetwork. The central controller 1002 receives the login credentials ofthe user through a transceiver.

The processing module 1004 is also configured to cross check the logincredentials of the user in the database 1010. The processing module 1004is also configured to retrieve a specific role assigned to the user. Thespecific assigned role may be based on the type/group of user. In someembodiments, the type of the user may include at least one of a familymember, an attendant, a nurse, a doctor, or a medicine administrator.The processing module 1004 may also provide an information read/writelayout, subsequent to login based on the specific assigned role of theuser. In some embodiments, the information read/write layout allows theuser to perform read and write operation.

The notification module 1006 of the central controller 1002 is adaptedto generate a first notification addressed to the plurality of userswhen a user interacts with the user interface. The plurality of usersmay include one of more groups of users. Further, one group of the usersis different from the other group of the users. The user interacts withthe user interface through at least one of a voice input, a text input,a video input, and a touch-based input.

The notification module 1006 is further configured to generate a secondnotification in case actionable item is not attended within a certaintime limit based on the first notification by the plurality of users,wherein the second notification is assigned to the next user within thesame or different group of users. The notification distribution modulemay distribute the generated first and second notifications to theplurality of users in different formats based on the profile of theplurality of users, the registered user device(s), or a location of theuser determined using location services from the user device. The formatof second notification is not changed when the second notification isassigned to the next user within the same group of users. In someembodiments, the format of second notification is changed when thesecond notification is assigned to the next user of different group ofusers, other than the group of users the second notification wasassigned earlier. Further, the next user to whom the second notificationis assigned is always above in hierarchy in the same or different groupof users.

In some embodiments, at least one notification is generated based on theuser interaction with the user interface. Further, the different formatsmay be based on the specific assigned role, the type of the user device,or location of the user device.

The voice processor 1008 is configured to receive at least one voiceinput comprising a request from the user through the user interface,wherein the request of the user may be presented on at least one userdevice associated with at least one user. In some embodiments, the voiceprocessor 1008 is configured to convert voice into at least one of atext message, and a video message. In an exemplary scenario, the userproviding the at least one voice input including a request may be anaged person residing in an old age home or a patient in a hospital, theat least one other user may be a care taker or a nurse. Examples of therequest may include such as, but not limited to, “I want to go to thebathroom”, “When will the doctor come to check me”, “I need food”, “Iwant to meet my son”, and so forth. The caretaker or nurse may receivethe request on their associated user device like a phone in form of atext message, voice message, video message, a haptic feedback, and soforth.

The voice processor 1008 is also configured to receive one or more voiceinputs including a response from the at least one user of the pluralityof users, wherein the response of the at least one user is presented ona user device of the user. For example, the caretaker or the nurse mayrespond through voice response or text response like “I am coming to seeyou”, “doctor will come at 4 PM”, “we will inform your son”, and soforth. The caretaker or nurse may record a message in theircorresponding user device, the voice processor may present the recordedmessage or the voice response or the text response to the user i.e. theaged person or the patient. In some embodiments, if the user is watchinga television, the response from the other user may flash on a part or onfull screen of the television.

The database 1010 may store profiles of the plurality of users, profilesof the users, specific roles' information of the users, and so forth.

An embodiment of the present disclosure provides a method forpersonalized care/resident management. The method includes: storing, ina database, profiles of a plurality of users; registering, in thedatabase, at least one corresponding user device for each of theplurality of users; receiving, by a processing module, login credentialsof the user through an interactive user interface on the user device;matching, by the processing module, the login credentials received forauthentication; retrieving, by the processing module, a profile of theuser post authentication; modifying, by the processing module,information layout of the user interface based on the profile of theuser; and generating, by a notification distribution module, a firstnotification addressed to the plurality of users when the user interactswith the user interface, the plurality of users having one of moregroups of users. One group of the users is different from the othergroup of the users. The user interacts with the user interface throughat least one of a voice input, a text input, a video input, and atouch-based input. Further, the method includes generating, by thenotification distribution module, a second notification in caseactionable item is not attended within a certain time limit based on thefirst notification by the plurality of users. The second notification isassigned to the next user within the same or different group of users.The method further includes distributing, by the notificationdistribution module, the generated first and second notifications to theplurality of users in different formats based on the profile of theplurality of users, the registered user device(s), or location of theuser determined using location services from the user device. The formatof second notification is not changed when the second notification isassigned to the next user within the same group of users. The format ofsecond notification is changed when the second notification isassignment to the next user of different group of users, other than thegroup of users the second notification was assigned earlier. The nextuser to whom the second notification is assigned is always above inhierarchy in the same or different group of users. The method alsoincludes: receiving, by a voice processor, at least one voice inputcomprising a request from the user through the user interface;presenting, by the voice processor, the request of the user on at leastone user device associated with at least one user; receiving, by thevoice processor, one or more voice inputs comprising a response from theat least one user of the plurality of users; and presenting, by thevoice processor, the response of the at least one user on a user deviceof the user.

In an aspect of the present disclosure, the method also includesconverting, by the voice processor, the at least one voice input and theone or more voice inputs into at least one of a text message, and avideo message.

In some embodiments, the notification may include at least one of anactionable item, or an information item for the user. Further, in someembodiments, the format of notifications may include at least one of atext message, an e-mail notification, an in-application message, or anin-application notification. The specific assigned role may be based onthe type/group of user. The different formats may be based on thespecific assigned role, the type of the user device, or location of theuser device.

Another embodiment of the present disclosure also provides anon-transitory computer-readable storage medium performing personalizedcare management, when executed by a computing device, cause thecomputing device (or user device) to store profiles of a plurality ofusers; register at least one corresponding user device for each of theplurality of users; receive login credentials of the user through aninteractive user interface on the user device; match the logincredentials received for authentication; retrieve a profile of the userpost authentication; modify information layout of the user interfacebased on the profile of the user; generate a first notificationaddressed to the plurality of users when the user interacts with theuser interface, the plurality of users having one of more groups ofusers, wherein one group of the users is different from the other groupof the users, wherein the user interacts with the user interface throughat least one of a voice input, a text input, a video input, and atouch-based input; generate a second notification in case actionableitem is not attended within a certain time limit based on the firstnotification by the plurality of users, wherein the second notificationis assigned to the next user within the same or different group ofusers; distribute the generated first and second notifications to theplurality of users in different formats based on the profile of theplurality of users, the registered user device(s), or location of theuser determined using location services from the user device, whereinthe format of second notification is not changed when the secondnotification is assigned to the next user within the same group ofusers, wherein the format of second notification is changed when thesecond notification is assignment to the next user of different group ofusers, other than the group of users the second notification wasassigned earlier, further wherein the next user to whom the secondnotification is assigned is always above in hierarchy in the same ordifferent group of users; receive at least one voice input comprising arequest from the user through the user interface; present the request ofthe user on at least one user device associated with at least one user;receive one or more voice inputs comprising a response from the at leastone user of the plurality of users; and present the response of the atleast one user on a user device of the user.

FIG. 11 is a block diagram 1100 illustrating system elements of thecentral controller 1002 communicating with external devices to receiveinput data related to non-scheduled actionable items, in accordance withan embodiment of the present disclosure. As shown, the centralcontroller 1002 includes a processing module 1004, a database 1010. Thedatabase 1010 may store various data and metadata pertaining to thepersonalized care management being provided to the care receivers.Accordingly, the database 1010 may store profiles of the authorizedcaregivers 1102 and profiles of the at least one care receiver 1104 thatmay be access by the authorized caregivers. The central controller 1002communicating with external devices including, but not limited to a QRscanner device 1106 and a Beacon Transmitter 1108.

According to one embodiment of the present disclosure, the communicationsystem for providing personalized care management comprises plurality ofuser devices corresponding to plurality of authorized caregivers, suchas a family member of the care receiver, an attendant for the carereceiver, a nurse for the care receiver, a doctor for the care receiver,or a medicine administrator for the care receiver, nurses, medicalpractitioners, friends, etc. Each user device may provide interactiveuser interface to facilitate the caregiver to provide input dataassociated with an actionable item being performed for at least one carereceiver. The care receiver may include one or more patients, old agedpersons, disabled or differently abled persons, dependent adults,dependent minors etc. The database 1010 may store multiple user ID andpasswords that may have been collected at the time of registration ofthe plurality of users. This facilitates in authorizing the users toaccess the data associated with the personalized care management of thecare receivers. The plurality of authorized users may have at least oneuser device registered with the care management system. The database1010 may also include profile of the plurality of authorized caregivers1102 that may further include a specific assigned role to each of thecaregivers/users. The specific assigned role helps in determining accessthat the users might have to information on user interface. The profileof the plurality of authorized caregivers/users may also help inidentifying to what all information does a user have access forperforming analysis as required for a particular care-receiver. Thedatabase 1010 is an integral part of the central controller 1002 and mayalso be configured for storing profiles of the care receivers 1104. Theprofiles of the authorized caregivers 1102 are stored in differentformats based on specific roles assigned to the authorized caregivers,and location of the plurality of user devices. The profiles of thecare-receivers 1104 may include personal details such as name, age,gender of the care-receivers, medical history, diet charts, behaviorpattern, physical and mental health condition, etc.

According to one embodiment of the present disclosure, the actionableitem may include the actions or events like medical care, psychologicalcare, non-medical care, daily routine care, providing medicines, foodand water to the care receivers, measuring vital readings of the carereceivers such as blood pressure, blood sugar levels, pulse rate,temperature etc.; providing personal hygiene care, and other services,being provided to the at least one care-receiver by the plurality ofauthorized caregivers.

In one embodiment of the present disclosure, the actionable itemincludes one of: a scheduled actionable item and a non-scheduledactionable item. The scheduled actionable item may include providingtimely medicines, food, checking blood pressure, blood sugar levelsetc., which occurs on fixed schedule or time intervals. Thenon-scheduled actionable item may include various events or actions thatare performed for a care-receiver without following a specific schedule,for example random bathing, frequent urination, work-outs, eatingmeals/snacks randomly. In other words, the non-schedule actionable itemsare random actions that may occur any number of times and during anytime within twenty-four hours. Thus, the non-scheduled actionable itemincludes one or more actions which are performed randomly for the carereceiver; whereas, the scheduled actionable item includes one or moreactions which are performed for the care receiver, according to aschedule prescribed by the corresponding authorized caregivers.

The non-scheduled actionable items are equally important to be recorded,since each recorded events or history, whether it is for a scheduledevent or if it is for a random event, will provide a better idea to thecare-giver about the condition of the care receiver being attended.Accordingly, the caregiver will be able to better analyze the conditionof the care receiver and thereby suggest further recommendations, suchas line of treatment, care plan, psychological assistance, diet plan,etc., as appropriate for the care-receivers.

Therefore, both the scheduled actionable items and the non-scheduledactionable items that are being performed for the care receivers, arerecorded in the system via the central controller 1002. The centralcontroller 1002 may be communicatively connected to the plurality ofuser devices through a communication network to facilitate theauthorized caregivers to analyze the profiles of the at least one carereceiver 1104 from a remote location.

The central controller 1002 also comprises the processing module 1004that is configured to receive, via the plurality of user devices, the atleast one input data based on the scheduled actionable item. Theprocessing module 1004 is also configured to receive, via the pluralityof user devices, the at least one input data based on the non-scheduledactionable item. Once the data related to both the scheduled actionableitem and the non-scheduled actionable item are recorded or inputted inthe processing module 1004, the profile of the at least one carereceiver 1104 is thereby based on the received at least one input data.Thereafter, the updated profile of the at least one care receiver 1104in saved in the database 1010 for future analysis. The authorizedcaregivers further analyze the updated profile of the at least one carereceiver 1104. Subsequently, the caregiver suggests furtherrecommendations, such as line of treatment, care plan, psychologicalassistance, diet plan, etc. to the care receiver.

Another embodiment of the present disclosure provides a method forproviding personalized care/resident management. The method comprisesthe steps of: configuring a plurality of user devices corresponding to aplurality of authorized caregivers, each user device providing aninteractive user interface for: providing input data associated with anactionable item being performed for at least one care receiver, whereinthe actionable item includes one of: a scheduled actionable item and anon-scheduled actionable item; configuring a database 1010 for storingprofiles of the authorized caregivers 1102 and profiles of the at leastone care receiver 1104; configuring a central controller 1002 connectedto the plurality of user devices through a communication network forfacilitating the authorized caregivers to analyze the profiles of the atleast one care receiver from a remote location; configuring a processingmodule 1004 for: receiving, via the plurality of user devices, the atleast one input data based on the scheduled actionable item; receiving,via the plurality of user devices, the at least one input data based onthe non-scheduled actionable item; updating the profile of the at leastone care receiver 1104 based on the received at least one input data;saving the updated profile of the at least one care receiver in thedatabase 1010; and facilitating the authorized caregivers to furtheranalyze the updated profile of the at least one care receiver 1104.

In one embodiment of the present disclosure, the at least one input databased on the non-scheduled actionable item is inputted into theprocessing module 1004 through at least one QR Code scanner device 1106.In another embodiment of the present disclosure, the at least one inputdata based on the non-scheduled actionable item is inputted into theprocessing module 1004 through at least one Beacon Transmitter 1108. TheQR Code Scanner device 1106 and the Beacon Transmitter 1108 receive thedigitized data associated with the non-scheduled actionable items. Thereceived data is further inputted into the central controller 1002 forprocessing by the processing module 1004.

The order in which the method as described above, is not intended to beconstrued as a limitation, and any number of the described method blockscan be combined in any order to implement the method or alternatemethods. Additionally, individual blocks may be deleted from the methodwithout departing from the spirit and scope of the subject matterdescribed herein. Furthermore, the method can be implemented in anysuitable hardware, software, firmware, or combination thereof. However,for ease of explanation, in the embodiments described below, the methodmay be considered to be implemented in the above-described system and/orthe apparatus and/or any electronic device (not shown).

The above description does not provide specific details of manufactureor design of the various components. Those of skill in the art arefamiliar with such details, and unless departures from those techniquesare set out, techniques, known, related art or later developed designsand materials should be employed. Those in the art are capable ofchoosing suitable manufacturing and design details.

Note that throughout the following discussion, numerous references maybe made regarding servers, services, engines, modules, interfaces,portals, platforms, or other systems formed from computing devices. Itshould be appreciated that the use of such terms is deemed to representone or more computing devices having at least one processor configuredto or programmed to execute software instructions stored on a computerreadable tangible, non-transitory medium or also referred to as aprocessor-readable medium. For example, a server can include one or morecomputers operating as a web server, database server, or other type ofcomputer server in a manner to fulfill described roles,responsibilities, or functions. Within the context of this document, thedisclosed devices or systems are also deemed to comprise computingdevices having a processor and a non-transitory memory storinginstructions executable by the processor that cause the device tocontrol, manage, or otherwise manipulate the features of the devices orsystems.

Some portions of the detailed description herein are presented in termsof algorithms and symbolic representations of operations on data bitsperformed by conventional computer components, including a centralprocessing unit (CPU), memory storage devices for the CPU, and connecteddisplay devices. These algorithmic descriptions and representations arethe means used by those skilled in the data processing arts to mosteffectively convey the substance of their work to others skilled in theart. An algorithm is generally perceived as a self-consistent sequenceof steps leading to a desired result. The steps are those requiringphysical manipulations of physical quantities. Usually, though notnecessarily, these quantities take the form of electrical or magneticsignals capable of being stored, transferred, combined, compared, andotherwise manipulated. It has proven convenient at times, principallyfor reasons of common usage, to refer to these signals as bits, values,elements, symbols, characters, terms, numbers, or the like.

It should be understood, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the discussion herein,it is appreciated that throughout the description, discussions utilizingterms such as “generating,” or “monitoring,” or “displaying,” or“tracking,” or “identifying,” “or receiving,” or the like, refer to theaction and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The methods illustrated throughout the specification, may be implementedin a computer program product that may be executed on a computer. Thecomputer program product may comprise a non-transitory computer-readablerecording medium on which a control program is recorded, such as a disk,hard drive, or the like. Common forms of non-transitorycomputer-readable media include, for example, floppy disks, flexibledisks, hard disks, magnetic tape, or any other magnetic storage medium,CD-ROM, DVD, or any other optical medium, a RAM, a PROM, an EPROM, aFLASH-EPROM, or other memory chip or cartridge, or any other tangiblemedium from which a computer can read and use.

Alternatively, the method may be implemented in transitory media, suchas a transmittable carrier wave in which the control program is embodiedas a data signal using transmission media, such as acoustic or lightwaves, such as those generated during radio wave and infrared datacommunications, and the like.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.It will be appreciated that several of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be combined intoother systems or applications. Various presently unforeseen orunanticipated alternatives, modifications, variations, or improvementstherein may subsequently be made by those skilled in the art withoutdeparting from the scope of the present disclosure as encompassed by thefollowing claim.

The claims, as originally presented and as they may be amended,encompass variations, alternatives, modifications, improvements,equivalents, and substantial equivalents of the embodiments andteachings disclosed herein, including those that are presentlyunforeseen or unappreciated, and that, for example, may arise fromapplicants/patentees and others.

It will be appreciated that variants of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be combined intomany other different systems or applications. Various presentlyunforeseen or unanticipated alternatives, modifications, variations, orimprovements therein may be subsequently made by those skilled in theart which are also intended to be encompassed by the following claims.

What is claimed is:
 1. A communication system for providing personalizedcare management comprising: a plurality of user devices corresponding toa plurality of authorized caregivers, each user device providing aninteractive user interface to: provide input data associated with anactionable item being performed for at least one care receiver, whereinthe actionable item includes one of: a scheduled actionable item and anon-scheduled actionable item; a database for storing profiles of theauthorized caregivers and profiles of the at least one care receiver; acentral controller connected to the plurality of user devices through acommunication network to facilitate the authorized caregivers to analyzethe profiles of the at least one care receiver from a remote location; aprocessing module configured to: receive, via the plurality of userdevices, the at least one input data based on the scheduled actionableitem; receive, via the plurality of user devices, the at least one inputdata based on the non-scheduled actionable item; update the profile ofthe at least one care receiver based on the received at least one inputdata; save the updated profile of the at least one care receiver in thedatabase; and facilitate the authorized caregivers to further analyzethe updated profile of the at least one care receiver.
 2. Thecommunication system of claim 1, wherein the profiles of the authorizedcaregivers are stored in different formats based on specific rolesassigned to the authorized caregivers, and location of the plurality ofuser devices.
 3. The communication system of claim 4, wherein theauthorized caregivers include at least one of: a family member of thecare receiver, an attendant for the care receiver, a nurse for the carereceiver, a doctor for the care receiver, or a medicine administratorfor the care receiver.
 4. The communication system of claim 1, whereinthe network is a wired or a wireless network, wherein the wirelessnetwork comprising at least one of: a mobile network, a satellitenetwork, a Wi-Fi, or a Wireless Local Area Network (WLAN).
 5. Thecommunication system of claim 1, wherein the at least one input dataincludes a voice input, a text input, a video input, and a touch-basedinput.
 6. The communication system of claim 1, wherein the actionableitem includes medical care, psychological care, non-medical care, dailyroutine care, being provided to the at least one care-receiver by theplurality of authorized caregivers.
 7. The communication system of claim1, wherein the at least one input data based on the non-scheduledactionable item is inputted into the processing module through at leastone QR Code scanner device.
 8. The communication system of claim 1,wherein the at least one input data based on the non-scheduledactionable item is inputted into the processing module through at leastone Beacon Transmitter.
 9. The communication system of claim 1, whereinthe non-scheduled actionable item includes one or more actions which areperformed randomly for the care receiver.
 10. The communication systemof claim 1, wherein the scheduled actionable item includes one or moreactions which are performed for the care receiver, according to aschedule prescribed by the corresponding authorized caregivers.
 11. Amethod for providing personalized care/resident management, the methodcomprising the steps of: configuring a plurality of user devicescorresponding to a plurality of authorized caregivers, each user deviceproviding an interactive user interface for: providing input dataassociated with an actionable item being performed for at least one carereceiver, wherein the actionable item includes one of: a scheduledactionable item and a non-scheduled actionable item; configuring adatabase for storing profiles of the authorized caregivers and profilesof the at least one care receiver; configuring a central controllerconnected to the plurality of user devices through a communicationnetwork for facilitating the authorized caregivers to analyze theprofiles of the at least one care receiver from a remote location;configuring a processing module for: receiving, via the plurality ofuser devices, the at least one input data based on the scheduledactionable item; receiving, via the plurality of user devices, the atleast one input data based on the non-scheduled actionable item;updating the profile of the at least one care receiver based on thereceived at least one input data; saving the updated profile of the atleast one care receiver in the database; and facilitating the authorizedcaregivers to further analyze the updated profile of the at least onecare receiver.
 12. The method of claim 11, further comprising the stepof storing the profiles of the authorized caregivers in differentformats based on specific roles assigned to the authorized caregivers,and location of the plurality of user devices.
 13. The method of claim11, wherein the authorized caregivers include at least one of: a familymember of the care receiver, an attendant for the care receiver, a nursefor the care receiver, a doctor for the care receiver, or a medicineadministrator for the care receiver.
 14. The method of claim 11, whereinthe at least one input data includes a voice input, a text input, avideo input, and a touch-based input.
 15. The method of claim 11,wherein the actionable item includes medical care, psychological care,non-medical care, daily routine care, being provided to the at least onecare-receiver by the plurality of authorized caregivers.
 16. The methodof claim 11, wherein the at least one input data based on thenon-scheduled actionable item is inputted into the processing modulethrough at least one QR Code scanner device.
 17. The method of claim 11,wherein the at least one input data based on the non-scheduledactionable item is inputted into the processing module through at leastone Beacon Transmitter.
 18. The method of claim 11, wherein thenon-scheduled actionable item includes one or more actions which areperformed randomly for the care receiver.
 19. The method of claim 11,wherein the scheduled actionable item includes one or more actions whichare performed for the care receiver, according to a schedule prescribedby the corresponding authorized caregivers.